System and method for intent-based active callback management

ABSTRACT

A system and method for intent-based active callback management, utilizing a cloud callback system comprising at least a profile manager, callback manager, interaction manager, media server, and environment analyzer, allowing users to call businesses, agents in contact centers, or other users who are connected to a cloud callback system, and, failing to connect to the individual they called, allow for an automatic callback object to be created, whereby the two users may be automatically called and bridged together at a time when both users are available.

CROSS-REFERENCE TO RELATED APPLICATIONS

application No. Date Filed Title Current Herewith A SYSTEM AND METHODFOR application INTENT- BASED ACTIVE CALLBACK MANAGEMENT which is acontinuation of: 16/542,577 Aug. 16, 2019 A SYSTEM AND METHOD FORINTENT- BASED ACTIVE CALLBACK MANAGEMENT which claims benefit of, andpriority to: 62/820,190 Mar. 18, 2019 A SYSTEM AND METHOD FOR INTENT-BASED ACTIVE CALLBACK MANAGEMENT the entire specification of each ofwhich is incorporated herein by reference.

BACKGROUND OF THE INVENTION Field of the Art

The disclosure relates to the field of contact center technology,specifically to the field of cloud-implemented automated callbacksystems.

Many businesses use groups of service representatives for communicatingwith clients who initiate communications with the business, such as bytelephone calls. To most efficiently use the time and skills of eachservice representative, the service representatives may be organizedinto groups based on a skill set. For example, the groupings may bebased on the representative's ability to handle client issues such asthe opening of new accounts, billing issues and customer service issueson existing accounts.

Discussion of the State of the Art

Typically, if a client calls such a business, voice prompt menu choicesenable the calling client to identify the issue for which the clientrequires service and the client is then queued for a service agentcapable of handling the identified issue. As such, it is expected thatclients who identify the purpose of their call as a “billing issue” willbe queued for, and connected to, a service representative with theability to handle billing issues. Similarly, it is expected that clientswho identify the purpose of their call as a “customer service issue”will be queued for, and connected to, a service representative with theability to handle customer service issues.

There are problems with existing communications systems, such as contactcenters, including the following two problems. First, the voice promptmenus that are used to channel callers to the queue for the appropriategroup of service agents are exacerbating to a client at best. It takessignificant time to navigate the layered menus of voice prompts.

Second, waiting on-hold while a connection, be it a phone call, webchat, video conference, or other interaction type, is maintained inqueue for connection to a service agent is also exacerbating to a clientat best.

In an effort to reduce customer exacerbation caused by having tomaintain a connection while on-hold in queue, secondary queue systemshave been developed. A typical secondary queue system obtains atelephone number at which the calling client can be reached when aservice representative is available (i.e., a call back number). Theclient disconnects, and then, at the proper time, a call back systemestablishes a connection to the client utilizing the call back numberand couples the client to an available representative without waitingon-hold in queue. One exemplary system is disclosed in U.S. Pat. No.6,563,921 to Williams et al. which is commonly assigned with the presentapplication.

While such a system may make the experience of waiting for a connectionto a service representative slightly less exasperating, it does notaddress the inconvenience of having to navigate an irritatingly slow andusually complicated voice prompt menu to enter the queue.

What is needed is a system and various methods for providing a callbackcloud and related services that overcome the limitations of the priorart noted above.

SUMMARY OF THE INVENTION

Accordingly, the inventor has conceived and reduced to practice, in apreferred embodiment of the invention, a system and methods forintent-based active callback management. The following non-limitingsummary of the invention is provided for clarity, and should beconstrued consistently with embodiments described in the detaileddescription below.

A system has been devised for intent-based active callback management,comprising: a profile manager comprising at least a processor, a memory,and a first plurality of programming instructions stored in the memoryand operating on the processor, wherein the first programminginstructions, when operating on the processor, cause the processor to:stores and maintains global user profiles; updates profiles based oncallback usage and performance patterns, as well as updates requested byusers; a callback manager comprising at least a processor, a memory, anda first plurality of programming instructions stored in the memory andoperating on the processor, wherein the first programming instructions,when operating on the processor, cause the processor to: receiving arequest for a callback to a callback recipient from a callbackrequester; instantiating a callback object; retrieving global profilesfor the callback requester and the callback recipient from the profilemanager; obtaining environmental context for callback requester andcallback recipient; determining a callback time based on the profile andthe environmental context and communicating it back to the callbackrecipient and the callback requester; connecting the two parties, whenthe two first and second called parties are online, and deleting thecallback object; an interaction manager comprising at least a processor,a memory, and a first plurality of programming instructions stored inthe memory and operating on the processor, wherein the first programminginstructions, when operating on the processor, cause the processor to:calling the other of a callback requester and callback recipient, whenthe first called party is online, as a second called party; connectingthe two parties, when the two first and second called parties areonline, and deleting the callback object; a media server comprising atleast a processor, a memory, and a first plurality of programminginstructions stored in the memory and operating on the processor,wherein the first programming instructions, when operating on theprocessor, cause the processor to: make calls and bridge them whenappropriate, under control of the interaction manager; and anenvironment analyzer comprising at least a processor, a memory, and afirst plurality of programming instructions stored in the memory andoperating on the processor, wherein the first programming instructions,when operating on the processor, cause the processor to: analyzeenvironment context data pertaining to the callback requester and thecallback recipient.

A method for intent-based active callback management has been devised,comprising the steps of: receiving a request for a callback to acallback recipient from a callback requester; instantiating a callbackobject; retrieving global profiles for the callback requester and thecallback recipient; obtaining environmental context for callbackrequester and callback recipient; determining a callback time based onthe profile and the environmental context, and communicating back to thecallback recipient and the callback requester; attempting a call to afirst called party when a callback time arrives, the first called partybeing one of either the callback requester or callback recipient;calling as a second called party, the other of the callback requesterand callback recipients, when the first called party is online; andconnecting the two first and second called parties when the secondcalled party is online, and deleting the callback object.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings illustrate several aspects and, together withthe description, serve to explain the principles of the inventionaccording to the aspects. It will be appreciated by one skilled in theart that the particular arrangements illustrated in the drawings aremerely exemplary, and are not to be considered as limiting of the scopeof the invention or the claims herein in any way.

FIG. 1 is a block diagram illustrating an exemplary system architecturefor operating a callback cloud, according to one aspect.

FIG. 2 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating over a public switched telephone networkand internet, to a variety of other brand devices and services,according to an embodiment.

FIG. 3 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including a calendar server, over apublic switched telephone network and internet, to a variety of otherbrand devices and services, according to an embodiment.

FIG. 4 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including a brand interface server, overa public switched telephone network and internet, to a variety of otherbrand devices and services, according to an embodiment.

FIG. 5 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including a brand interface server andintent analyzer, over a public switched telephone network and internet,to a variety of other brand devices and services, according to anembodiment.

FIG. 6 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including a privacy server, over a publicswitched telephone network and internet, to a variety of other branddevices and services, according to an embodiment.

FIG. 7 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including a bot server, over a publicswitched telephone network and internet, to a variety of other branddevices and services, according to an embodiment.

FIG. 8 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating including an operations analyzer over apublic switched telephone network and internet, to a variety of otherbrand devices and services, according to an embodiment.

FIG. 9 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a brand interface server, an intentanalyzer, and a broker server, operating over a public switchedtelephone network and internet, to a variety of other brand devices andservices, according to an embodiment.

FIG. 10 is a diagram illustrating trust circles of levels of privacy fora user of a callback cloud, according to an aspect.

FIG. 11 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, according to an embodiment.

FIG. 12 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a calendar server,according to an embodiment.

FIG. 13 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including gathering ofenvironmental context data of users, according to an embodiment.

FIG. 14 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a brand interfaceserver and intent analyzer, according to an embodiment.

FIG. 15 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a privacy server,according to an embodiment.

FIG. 16 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a bot server,according to an embodiment.

FIG. 17 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including an operationsanalyzer, according to an embodiment.

FIG. 18 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a brand interfaceserver, intent analyzer, and broker server, according to an embodiment.

FIG. 19 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, according to an embodiment.

FIG. 20 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a calendar server, according to anembodiment.

FIG. 21 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server, according to anembodiment.

FIG. 22 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server and intentanalyzer, according to an embodiment.

FIG. 23 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a privacy server, according to anembodiment.

FIG. 24 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a bot server, according to an embodiment.

FIG. 25 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including an operations analyzer, according to anembodiment.

FIG. 26 is a block diagram illustrating an exemplary hardwarearchitecture of a computing device.

FIG. 27 is a block diagram illustrating an exemplary logicalarchitecture for a client device.

FIG. 28 is a block diagram showing an exemplary architecturalarrangement of clients, servers, and external services.

FIG. 29 is another block diagram illustrating an exemplary hardwarearchitecture of a computing device.

FIG. 30 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server, intentanalyzer, and broker server, according to an embodiment.

DETAILED DESCRIPTION

The inventor has conceived, and reduced to practice, a system and methodfor intent-based active callback management.

One or more different aspects may be described in the presentapplication. Further, for one or more of the aspects described herein,numerous alternative arrangements may be described; it should beappreciated that these are presented for illustrative purposes only andare not limiting of the aspects contained herein or the claims presentedherein in any way. One or more of the arrangements may be widelyapplicable to numerous aspects, as may be readily apparent from thedisclosure. In general, arrangements are described in sufficient detailto enable those skilled in the art to practice one or more of theaspects, and it should be appreciated that other arrangements may beutilized and that structural, logical, software, electrical and otherchanges may be made without departing from the scope of the particularaspects. Particular features of one or more of the aspects describedherein may be described with reference to one or more particular aspectsor figures that form a part of the present disclosure, and in which areshown, by way of illustration, specific arrangements of one or more ofthe aspects. It should be appreciated, however, that such features arenot limited to usage in the one or more particular aspects or figureswith reference to which they are described. The present disclosure isneither a literal description of all arrangements of one or more of theaspects nor a listing of features of one or more of the aspects thatmust be present in all arrangements.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only, and are not to betaken as limiting the disclosure in any way.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or morecommunication means or intermediaries, logical or physical.

A description of an aspect with several components in communication witheach other does not imply that all such components are required. To thecontrary, a variety of optional components may be described toillustrate a wide variety of possible aspects and in order to more fullyillustrate one or more aspects. Similarly, although process steps,method steps, algorithms or the like may be described in a sequentialorder, such processes, methods and algorithms may generally beconfigured to work in alternate orders, unless specifically stated tothe contrary. In other words, any sequence or order of steps that may bedescribed in this patent application does not, in and of itself,indicate a requirement that the steps be performed in that order. Thesteps of described processes may be performed in any order practical.Further, some steps may be performed simultaneously despite beingdescribed or implied as occurring non-simultaneously (e.g., because onestep is described after the other step). Moreover, the illustration of aprocess by its depiction in a drawing does not imply that theillustrated process is exclusive of other variations and modificationsthereto, does not imply that the illustrated process or any of its stepsare necessary to one or more of the aspects, and does not imply that theillustrated process is preferred. Also, steps are generally describedonce per aspect, but this does not mean they must occur once, or thatthey may only occur once each time a process, method, or algorithm iscarried out or executed. Some steps may be omitted in some aspects orsome occurrences, or some steps may be executed more than once in agiven aspect or occurrence.

When a single device or article is described herein, it will be readilyapparent that more than one device or article may be used in place of asingle device or article. Similarly, where more than one device orarticle is described herein, it will be readily apparent that a singledevice or article may be used in place of the more than one device orarticle.

The functionality or the features of a device may be alternativelyembodied by one or more other devices that are not explicitly describedas having such functionality or features. Thus, other aspects need notinclude the device itself.

Techniques and mechanisms described or referenced herein will sometimesbe described in singular form for clarity. However, it should beappreciated that particular aspects may include multiple iterations of atechnique or multiple instantiations of a mechanism unless notedotherwise. Process descriptions or blocks in figures should beunderstood as representing modules, segments, or portions of code whichinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Alternate implementations areincluded within the scope of various aspects in which, for example,functions may be executed out of order from that shown or discussed,including substantially concurrently or in reverse order, depending onthe functionality involved, as would be understood by those havingordinary skill in the art.

Definitions

“Callback” as used herein refers to an instance of an individual beingcontacted after their initial contact was unsuccessful. For instance, ifa first user calls a second user on a telephone, but the second userdoes not receive their call for one of numerous reasons includingturning off their phone or simply not picking up, the second user maythen place a callback to the first user once they realize they missedtheir call. This callback concept applies equally to many forms ofinteraction that need not be restricted to telephone calls, for exampleincluding (but not limited to) voice calls over a telephone line, videocalls over a network connection, or live text-based chat such as webchat or short message service (SMS) texting. While a callback (andvarious associated components, methods, and operations taught herein)may also be used with an email communication despite the inherentlyasynchronous nature of email (participants may read and reply to emailsat any time, and need not be interacting at the same time or while otherparticipants are online or available), the preferred usage as taughtherein refers to synchronous communication (that is, communication whereparticipants are interacting at the same time, as with a phone call orchat conversation).

“Callback object” as used herein means a data object representingcallback data, such as the identities and call information for a firstand second user, the parameters for a callback including what time itshall be performed, and any other relevant data for a callback to becompleted based on the data held by the callback object.

“Latency period” as used herein refers to the period of time betweenwhen a Callback Object is created and the desired Callback is initiated,for example, if a callback object is created and scheduled for a timefive hours from the creation of the object, and the callback initiateson-time in five hours, the latency period is equal to the five hoursbetween the callback object creation and the callback initiation.

“Brand” as used herein means a possible third-party service or devicethat may hold a specific identity, such as a specific MAC address, IPaddress, a username or secret key which can be sent to a cloud callbacksystem for identification, or other manner of identifiable device orservice that may connect with the system. Connected systems or servicesmay include a Private Branch Exchange (“PBX”), call router, chat serverwhich may include text or voice chat data, a Customer RelationshipManagement (“CRM”) server, an Automatic Call Distributor (“ACD”), or aSession Initiation Protocol (“SIP”) server.

Conceptual Architecture

FIG. 1 is a block diagram of a preferred embodiment of the invention,illustrating an exemplary architecture of a system 100 for providing acallback cloud service. According to the embodiment, callback cloud 101may receive requests 140 via a plurality of communications networks suchas a public switched telephone network (PSTN) 103 or the Internet 102.These requests may comprise a variety of communication and interactiontypes, for example including (but not limited to) voice calls over atelephone line, video calls over a network connection, or livetext-based chat such as web chat or short message service (SMS) textingvia PSTN 103. Such communications networks may be connected to aplurality of consumer endpoints 110 and enterprise endpoints 120 asillustrated, according to the particular architecture of communicationnetwork involved. Exemplary consumer endpoints 110 may include, but arenot limited to, traditional telephones 111, cellular telephones 112,mobile tablet computing devices 113, laptop computers 114, or desktoppersonal computers (PC) 115. Such devices may be connected to respectivecommunications networks via a variety of means, which may includetelephone dialers, VOIP telecommunications services, web browserapplications, SMS text messaging services, or other telephony or datacommunications services. It will be appreciated by one having ordinaryskill in the art that such means of communication are exemplary, andmany alternative means are possible and becoming possible in the art,any of which may be utilized as an element of system 100 according tothe invention.

A PSTN 103 or the Internet 102 (and it should be noted that not allalternate connections are shown for the sake of simplicity, for examplea desktop PC 126 may communicate via the Internet 102) may be furtherconnected to a plurality of enterprise endpoints 120, which may comprisecellular telephones 121, telephony switch 122, desktop environment 125,internal Local Area Network (LAN) or Wide-Area Network (WAN) 130, andmobile devices such as tablet computing device 128. As illustrated,desktop environment 125 may include both a telephone 127 and a desktopcomputer 126, which may be used as a network bridge to connect atelephony switch 122 to an internal LAN or WAN 130, such that additionalmobile devices such as tablet PC 128 may utilize switch 122 tocommunicate with PSTN 102. Telephone 127 may be connected to switch 122or it may be connected directly to PSTN 102. It will be appreciated thatthe illustrated arrangement is exemplary, and a variety of arrangementsthat may comprise additional devices known in the art are possible,according to the invention.

Callback cloud 101 may respond to requests 140 received fromcommunications networks with callbacks appropriate to the technologyutilized by such networks, such as data or Voice over Internet Protocol(VOIP) callbacks 145, 147 sent to Internet 102, or time-divisionmultiplexing (TDM) such as is commonly used in cellular telephonynetworks such as the Global System for Mobile Communications (GSM)cellular network commonly used worldwide, or VOIP callbacks to PSTN 103.Data callbacks 147 may be performed over a variety of Internet-enabledcommunications technologies, such as via e-mail messages, applicationpop-ups, or Internet Relay Chat (IRC) conversations, and it will beappreciated by one having ordinary skill in the art that a wide varietyof such communications technologies are available and may be utilizedaccording to the invention. VOIP callbacks may be made using either, orboth, traditional telephony networks such as PSTN 103 or over VOIPnetworks such as Internet 102, due to the flexibility to the technologyinvolved and the design of such networks. It will be appreciated thatsuch callback methods are exemplary, and that callbacks may be tailoredto available communications technologies according to the invention.

Additionally, callback cloud 101 may receive estimated wait time (EWT)information from an enterprise 120 such as a contact center. Thisinformation may be used to estimate the wait time for a caller beforereaching an agent (or other destination, such as an automated billingsystem), and determine whether to offer a callback proactively beforethe customer has waited for long. EWT information may also be used toselect options for a callback being offered, for example to determineavailability windows where a customer's callback is most likely to befulfilled (based on anticipated agent availability at that time), or tooffer the customer a callback from another department or location thatmay have different availability. This enables more detailed and relevantcallback offerings by incorporating live performance data from anenterprise, and improves customer satisfaction by saving additional timewith preselected recommendations and proactively-offered callbacks.

FIG. 2 is a block diagram illustrating an exemplary system architecturefor a callback cloud operating over a public switched telephone networkand the Internet, and connecting to a variety of other brand devices andservices, according to an embodiment. A collection of user brands 210may be present either singly or in some combination, possibly includinga Public Branch Exchange (“PBX”) 211, a Session Initiation Protocol(“SIP”) server 212, a Customer Relationship Management (“CRM”) server213, a call router 214, or a chat server 215, or some combination ofthese brands. These brands 210 may communicate over a combination of, oronly one of, a Public Switched Telephone Network (“PSTN”) 103, and theInternet 102, to communicate with other devices including a callbackcloud 220, a company phone 121, or a personal cellular phone 112. A SIPserver 212 is responsible for initiating, maintaining, and terminatingsessions of voice, video, and text or other messaging protocols,services, and applications, including handling of PBX 211 phonesessions, CRM server 213 user sessions, and calls forwarded via a callrouter 214, all of which may be used by a business to facilitate diversecommunications requests from a user or users, reachable by phone 121,112 over either PSTN 103 or the Internet 102. A chat server 215 may beresponsible for maintaining one or both of text messaging with a user,and automated voice systems involving technologies such as an AutomatedCall Distributor (“ACD”), forwarding relevant data to a call router 214and CRM server 213 for further processing, and a SIP server 212 forgenerating communications sessions not run over the PSTN 103. Varioussystems may also be used to monitor their respective interactions (forexample, chat session by a chat server 215 or phone calls by an ACD orSIP server 212), to track agent and resource availability for producingEWT estimations.

When a user calls from a mobile device 112 or uses some communicationapplication such as (for example, including but not limited to) SKYPE™or instant messaging, which may also be available on a laptop or othernetwork endpoint other than a cellular phone 112, they may be forwardedto brands 210 operated by a business in the manner described herein. Forexample, a cellular phone call my be placed over PSTN 103 before beinghandled by a call router 214 and generating a session with a SIP server212, the SIP server creating a session with a callback cloud 220 with aprofile manager 221 if the call cannot be completed, resulting in acallback being required. A profile manager 221 manages the storage,retrieval, and updating of user profiles, including global and localuser profiles. The profile manager 221, which may be located in acallback cloud 220 receives initial requests to connect to callbackcloud 220, and forwards relevant user profile information to a callbackmanager 223, which may further request environmental context data froman environment analyzer 222. Environmental context data may include (forexample, and not limited to) recorded information about when a callbackrequester or callback recipient may be suspected to be driving orcommuting from work, for example, and may be parsed from online profilesor online textual data, using an environment analyzer 222.

A callback manager 223 centrally manages all callback data, creating acallback programming object which may be used to manage the data for aparticular callback, and communicates with an interaction manager 224which handles requests to make calls and bridge calls, which go out to amedia server 225 which actually makes the calls as requested. Forexample, interaction manager 224 may receive a call from a callbackrequester, retrieve callback parameters for that callback requester fromthe callback manager 223, and cause the media server 225 to make a callto a callback recipient while the callback requester is still on theline, thus connecting the two parties. After the call is connected, thecallback programming object used to make the connection may be deleted.The interaction manager 224 may subsequently provide changed callbackparameters to the callback manager 223 for use or storage. In this way,the media server 225 may be altered in the manner in which it makes andbridges calls when directed, but the callback manager 223 does not needto adjust itself, due to going through an intermediary component, theinteraction manager 224, as an interface between the two. A media server225, when directed, may place calls and send messages, emails, orconnect voice over IP (“VoIP”) calls and video calls, to users over aPSTN 103 or the Internet 102. Callback manager 223 may work with auser's profile as managed by a profile manager 221, with environmentalcontext from an environment analyzer 222 as well as (if provided) EWTinformation for any callback recipients (for example, contact centeragents with the appropriate skills to address the callback requestor'sneeds, or online tech support agents to respond to chat requests), todetermine an appropriate callback time for the two users (a callbackrequestor and a callback recipient), interfacing with an interactionmanager 224 to physically place and bridge the calls with a media server225. In this way, a user may communicate with another user on a PBXsystem 211, or with automated services hosted on a chat server 215, andif they do not successfully place their call or need to be called backby a system, a callback cloud 220 may find an optimal time to bridge acall between the callback requestor and callback recipient, asnecessary.

FIG. 3 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a calendar server operating over a publicswitched telephone network and the Internet, and connected to a varietyof other brand devices and services, according to an embodiment.According to this embodiment, many user brands 310 are present,including PBX system 311, a SIP server 312, a CRM server 313, a callrouter 314, and a chat server 315, which may be connected variously toeach other as shown, and connected to a PSTN 103 and the Internet 102,which further connect to a cellular phone 112 and a landline 121 orother phone that may not have internet access. As further shown,callback cloud 320 contains multiple components, including a calendarserver 321, profile manager 322, environment analyzer 323, callbackmanager 324, interaction manager 325, and media server 326, whichsimilarly to user brands 310 may be interconnected in various ways asdepicted in the diagram, and connected to either a PSTN 103 or theinternet 102.

A calendar server 321, according to the embodiment, is a server whichmay store and retrieve, either locally or from internet-enabled servicesassociated with a user, calendars which hold data on what times a usermay be available or busy (or some other status that may indicate otherspecial conditions, such as to allow only calls from certain sources)for a callback to take place. A calendar server 321 connects to theinternet 102, and to a profile manager 322, to determine the times acallback requestor and callback recipient may both be available.

FIG. 4 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a brand interface server, operating overa public switched telephone network and the Internet, and connected to avariety of other brand devices and services, according to an embodiment.According to this embodiment, many user brands 410 are present,including PBX system 411, a SIP server 412, a CRM server 413, a callrouter 414, and a chat server 415, which may be connected variously toeach other as shown, and connected to a PSTN 103 and the Internet 102,which further connect to a cellular phone 112 and a landline 121 orother phone that may not have internet access. As further shown,callback cloud 420 contains multiple components, including a profilemanager 421, environment analyzer 422, callback manager 423, interactionmanager 424, and media server 425, which similarly to user brands 410may be interconnected in various ways as depicted in the diagram, andconnected to either a PSTN 103 or the internet 102.

Present in this embodiment is a brand interface server 430, which mayexpose the identity of, and any relevant API's or functionality for, anyof a plurality of connected brands 410, to elements in a callback cloud420. In this way, elements of a callback cloud 420 may be able toconnect to, and interact more directly with, systems and applicationsoperating in a business' infrastructure such as a SIP server 412, whichmay be interfaced with a profile manager 421 to determine the exactnature of a user's profiles, sessions, and interactions in the systemfor added precision regarding their possible availability and mostimportantly, their identity.

FIG. 5 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a brand interface server and intentanalyzer, operating over a public switched telephone network and theInternet, and connected to a variety of other brand devices andservices, according to an embodiment. According to this embodiment, manyuser brands 510 are present, including PBX system 511, a SIP server 512,a CRM server 513, a call router 514, and a chat server 515, which may beconnected variously to each other as shown, and connected to a PSTN 103and the Internet 102, which further connect to a cellular phone 112 anda landline 121 or other phone that may not have internet access. Furthershown is a callback cloud 520 contains multiple components, including aprofile manager 521, environment analyzer 522, callback manager 523,interaction manager 524, and media server 525, which similarly to userbrands 510 may be interconnected in various ways as depicted in thediagram, and connected to either a PSTN 103 or the internet 102.

Present in this embodiment is a brand interface server 530, which mayexpose the identity of, and any relevant API's or functionality for, anyof a plurality of connected brands 510, to elements in a callback cloud520. In this way, elements of a callback cloud 520 may be able toconnect to, and interact more directly with, systems and applicationsoperating in a business' infrastructure such as a SIP server 512, whichmay be interfaced with a profile manager 521 to determine the exactnature of a user's profiles, sessions, and interactions in the systemfor added precision regarding their possible availability and mostimportantly, their identity. Also present in this embodiment is anintent analyzer 540, which analyzes spoken words or typed messages froma user that initiated the callback request, to determine their intentfor a callback. For example, their intent may be to have an hour-longmeeting, which may factor into the decision by a callback cloud 520 toplace a call shortly before one or both users may be required to startcommuting to or from their workplace. Intent analysis may utilize anycombination of text analytics, speech-to-text transcription, audioanalysis, facial recognition, expression analysis, posture analysis, orother analysis techniques, and the particular technique or combinationof techniques may vary according to such factors as the device type orinteraction type (for example, speech-to-text may be used for avoice-only call, while face/expression/posture analysis may beappropriate for a video call), or according to preconfigured settings(that may be global, enterprise-specific, user-specific,device-specific, or any other defined scope).

FIG. 6 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a privacy server, operating over a publicswitched telephone network and the Internet, and connected to a varietyof other brand devices and services, according to an embodiment.According to this embodiment, many user brands 610 are present,including PBX system 611, a SIP server 612, a CRM server 613, a callrouter 614, and a chat server 615, which may be connected variously toeach other as shown, and connected to a PSTN 103 and the Internet 102,which further connect to a cellular phone 112 and a landline 121 orother phone that may not have internet access. As further shown, acallback cloud 620 contains multiple components, including a profilemanager 622, environment analyzer 623, callback manager 624, interactionmanager 625, and media server 626, which similarly to user brands 610may be interconnected in various ways as depicted in the diagram, andconnected to either a PSTN 103 or the internet 102.

In this embodiment, a privacy server 621 may connect to the internet102, and to a profile manager 622 as well as a callback manager 624, andallows for callback requestors to first be validated using trust-circlesto determine if they are a trusted user. A trusted user may be definedusing a variety of criteria (that may vary according to the user,interaction, device, enterprise, or other context), and may for examplecomprise a determination of whether the callback requestor is a friendor family member, or is using a trusted brand such as a piece ofequipment from the same company that the callback recipient works at, orif the callback requestor is untrusted or is contacting unknownrecipients, to determine if a callback request is permitted based onuser settings. Further, a privacy server 621 may encrypt one or both ofincoming and outgoing data from a callback manager 624 in such a way asto ensure that, for example, a callback recipient might not know whorequested the callback, or their profile may not be visible to therecipient, or vice versa, and other privacy options may also be enabledas needed by a corporation. Encryption may utilize public or privatekeys, or may utilize perfect forward secrecy (such that even theenterprise routing the call cannot decrypt it), or other encryptionschema or combinations thereof that may provide varying features ordegrees of privacy, security, or anonymity (for example, one enterprisemay permit anonymous callbacks while another may require a user toidentify themselves and may optionally verify this identification).

FIG. 7 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a bot server, operating over a publicswitched telephone network and the Internet, and connected to a varietyof other brand devices and services, according to an embodiment.According to this embodiment, many user brands 710 are present,including PBX system 711, a SIP server 712, a CRM server 713, a callrouter 714, and a chat server 715, which may be connected variously toeach other as shown, and connected to a PSTN 103 and the Internet 102,which further connect to a cellular phone 112 and a landline 121 orother phone that may not have internet access. As further shown, acallback cloud 720 contains multiple components, including a profilemanager 721, environment analyzer 722, callback manager 723, interactionmanager 725, and media server 726, which similarly to user brands 710may be interconnected in various ways as depicted in the diagram, andconnected to either a PSTN 103 or the internet 102.

In the present embodiment, a bot server 724 also is present in acallback cloud 720, which allows for communication with a callbackrequestor. Bot server 724 allows a user to specify, through anyavailable data type such as (including, but not limited to) SMS texting,email, or audio data, any desired parameters for the callback they wouldlike to request. This is similar to an ACD system used by individualcall-centers, but exists as a separate server 724 in a cloud service 720which may then be configured as-needed by a hosting company, and behavesakin to an automated secretary, taking user information down to specifya callback at a later time from the callback recipient.

FIG. 8 is a block diagram illustrating an exemplary system architecturefor a callback cloud including an operations analyzer operating over apublic switched telephone network and the Internet, and connected to avariety of other brand devices and services, according to an embodiment.According to this embodiment, many user brands 810 are present,including PBX system 811, a SIP server 812, a CRM server 813, a callrouter 814, and a chat server 815, which may be connected variously toeach other as shown, and connected to a PSTN 103 and the Internet 102,which further connect to a cellular phone 112 and a landline 121 orother phone that may not have internet access. As further shown, acallback cloud 820 contains multiple components, including a profilemanager 821, environment analyzer 822, callback manager 823, interactionmanager 825, and media server 826, which similarly to user brands 810may be interconnected in various ways as depicted in the diagram, andconnected to either a PSTN 103 or the internet 102.

In this embodiment, an operations analyzer 824 is present, which maydetermine a particular channel to be used to reach a callback recipientand callback requestor, for example (and not limited to), VoIP servicessuch as SKYPE™ or DISCORD™, a PSTN phone connection, any particularphone number or user accounts to connect using, or other service, todetermine the optimal method with which to reach a user during acallback. An operations analyzer 824 may also analyze and determine thepoints of failure in a callback cloud 820, if necessary, for example ifa callback attempt fails to connect operations analyzer 824 may bridge acallback requestor and recipient using an alternate communicationchannel to complete the callback at the scheduled time.

FIG. 9 is a block diagram illustrating an exemplary system architecturefor a callback cloud including a brand interface server, an intentanalyzer, and a broker server, operating over a public switchedtelephone network and internet, and connected to a variety of otherbrand devices and services, according to an embodiment. According tothis embodiment, many user brands 910 are present, including PBX system911, a SIP server 912, a CRM server 913, a call router 914, and a chatserver 915, which may be connected variously to each other as shown, andconnected to a PSTN 103 and the Internet 102, which further connect to acellular phone 112 and a landline 121 or other phone that may not haveinternet access. As further shown, a callback cloud 920 containsmultiple components, including a profile manager 921, environmentanalyzer 922, callback manager 923, interaction manager 924, and mediaserver 925, which similarly to user brands 910 may be interconnected invarious ways as depicted in the diagram, and connected to either a PSTN103 or the internet 102. Also present are a plurality of networkendpoints 960, 970, connected to either or both of the internet 102 anda PSTN 103, such network endpoints representing contact points otherthan a landline 121 or cell phone 112, including laptops, desktops,tablet computers, or other communication devices.

Present in this embodiment is a brand interface server 930, which mayexpose the identity of, and any relevant API's or functionality for, anyof a plurality of connected brands 910, to an intent analyzer 940. Inthis way, elements of a callback cloud 920 may be able to connect to,and interact more directly with, systems and applications operating in abusiness' infrastructure such as a SIP server 912, which may beinterfaced with a profile manager 921 to determine the exact nature of auser's profiles, sessions, and interactions in the system for addedprecision regarding their possible availability and most importantly,their identity. An intent analyzer 940 may analyze spoken words or typedmessages from a user that initiated the callback request, to determinetheir intent for a callback, as well as forward data received from abrand interface server. For example, their intent may be to have anhour-long meeting, which may factor into the decision by a callbackcloud 920 to place a call shortly before one or both users may berequired to start commuting to or from their workplace. An intentanalyzer 940 may forward all data through a broker server 950 which mayallocate specific actions and responses to take between third-partybrands 910 and callback cloud 920 components, as needed, as well asforward all data from the exposed and interfaced elements with thecallback cloud 920.

FIG. 10 is a diagram illustrating trust circles of levels of privacy fora user of a callback cloud, according to an aspect. These trust circlesare data constructs enforced by a privacy server 621 which aredetermined with a profile manager 622, which indicate the level of trustthat callers may possess, and therefore the system's ability to schedulea callback with the caller and the recipient. A caller who calls from arecognized brand 1010, for example a company's phone forwarded throughtheir PBX 611, may be recognized as having the highest level of trust,due to coming from a recognized source within the same organization.Family 1020 may (for example) be the second highest level of trust,allowing for just as many privileges with callbacks, or perhapsrestricting callback requests to only certain hours, to prevent usersfrom being disrupted during certain work hours. A callback recipient'sfriends 1030 may occupy a level of trust lower than that of family,representing users less-trusted than family 1020 callers, and may yethave more restricted access to making callback requests for a user, anda continuing, descending hierarchy may be used to model additionallevels of trust. For example, additional trust levels may include (butare not limited to) social media 1040 recognized users, colleagues 1050which may represent individuals only loosely affiliated with a potentialcallback recipient, and untrusted 1060, representing users who are knownto the system and deemed banned or untrustworthy, having the lowestability to request an automated callback connection with a user. Afurther level of trust may exist, outside of the trust-circle paradigm,representing unknown contacts 1070, which, depending on the settings foran individual user or an organization using a callback cloud system 620,may be unable to request callbacks, or may only be able to requestcallbacks at certain restricted hours until they are set to a higherlevel of trust in the system, according to a preferred embodiment.

As shown in FIG. 10, trust circles need not be implicitly hierarchicalin nature and may overlap in various ways similar to a logical Venndiagram. For example one individual may be a friend and also known onsocial media, or someone may be both family and a colleague (as iscommonplace in family businesses or large companies that may employ manypeople). As shown, anybody may be considered “untrusted” regardless oftheir other trust groupings, for example if a user does not wish toreceive callbacks from a specific friend or coworker. While thearrangement shown is one example, it should be appreciated that a widevariety of numerous overlapping configuration may be possible witharbitrary complexity, as any one person may be logically placed withinany number of groups as long as the trust groupings themselves are notexclusive (such as a group for coworkers and one for individuals outsidethe company).

Expanding on the notion of trust circles, there may also be logical“ability” circles that correspond to various individuals' capabilitiesand appropriateness for various issues, such as (for example) techsupport skill or training with specific products, or whether a member ofa brand 1010 is actually a member of the best brand to handle a specificreason for a callback, based on the callback request context. Forexample, a customer requesting a callback for assistance with booking aflight may not be adequately served by employees of airlines that don'toffer flights to their intended destination, so combining the brandtrust zone 1010 with a capability map would indicate to the callbacksystem which individuals are more appropriate for the callback inquestion. This expands from merely trusting certain users and discardingothers, to a form of automated virtual concierge service that finds theuser for a callback request that is most capable and relevant to therequest, ensuring optimum handling of the callback requestor's needs.

FIG. 11 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, according to an embodiment.According to an embodiment, a callback cloud 220 must receive a requestfor a callback to a callback recipient, from a callback requester 1110.This refers to an individual calling a user of a cloud callback system220, being unable to connect for any reason, and the system allowing thecaller to request a callback, thus becoming the callback requester, fromthe callback recipient, the person they were initially unable to reach.A callback object is instantiated 1120, using a callback manager 223,which is an object with data fields representing the various parts ofcallback data for a callback requester and callback recipient, and anyrelated information such as what scheduled times may be possible forsuch a callback to take place. Global profiles may then be retrieved1130 using a profile manager 221 in a cloud callback system, as well asan analysis of environmental context data 1140, allowing for the systemto determine times when a callback may be possible for a callbackrequestor and callback recipient both 1150. When such a time arrives, afirst callback is attempted 1160 to the callback requestor or callbackrecipient, and if this succeeds, a second call is attempted to thesecond of the callback requestor and callback recipient 1170, allowing amedia server 225 to bridge the connection when both are online, beforedeleting the callback object 1180.

FIG. 12 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a calendar server,according to an embodiment. According to an embodiment, a callback cloud320 must receive a request for a callback to a callback recipient, froma callback requester 1205. This refers to an individual calling a userof a cloud callback system 320, being unable to connect for any reason,and the system allowing the caller to request a callback, thus becomingthe callback requester, from the callback recipient, the person theywere initially unable to reach. A callback object is instantiated 1210,using a callback manager 324, which is an object with data fieldsrepresenting the various parts of callback data for a callback requesterand callback recipient, and any related information such as whatscheduled times may be possible for such a callback to take place.Global profiles may then be retrieved 1215 using a profile manager 322which manages the storage and retrieval of user profiles, includingglobal and local user profiles. The profile manager 322, which may belocated in a cloud callback system, interfaces with user-specificcalendars 1220 to find dates and timeslots on their specific calendarsthat they both may be available 1225 through use of a calendar server321, as well as an analysis of environmental context data 1230, allowingfor the system to determine times when a callback may be possible for acallback requestor and callback recipient both 1235. When such a timearrives, a first callback is attempted 1240 to the callback requestor orcallback recipient, and if this succeeds, a second call is attempted tothe second of the callback requestor and callback recipient 1245,allowing a media server 326 to bridge the connection when both areonline, before deleting the callback object 1250.

FIG. 13 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including gathering ofenvironmental context data of users, according to an embodiment.According to an embodiment, a callback cloud 420 may interface with abrand interface server 430, which may interface with third-party orproprietary brands of communications devices and interfaces such asautomated call distributor systems 1305. Through this brand interface,the system may receive a request for a callback to a callback recipient,from a callback requester 1310. This refers to an individual calling auser of a cloud callback system 420, being unable to connect for anyreason, and the system allowing the caller to request a callback, thusbecoming the callback requester, from the callback recipient, the personthey were initially unable to reach. A callback object is instantiated1315, using a callback manager 423, which is an object with data fieldsrepresenting the various parts of callback data for a callback requesterand callback recipient, and any related information such as whatscheduled times may be possible for such a callback to take place.Global profiles may then be retrieved 1320 using a profile manager 421in a cloud callback system, as well as an analysis of environmentalcontext data 1325, allowing for the system to determine times when acallback may be possible for a callback requestor and callback recipientboth 1330. When such a time arrives, a first callback is attempted 1335to the callback requestor or callback recipient, and if this succeeds, asecond call is attempted to the second of the callback requestor andcallback recipient 1340, allowing a media server 425 to bridge theconnection when both are online, before deleting the callback object1345.

FIG. 14 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a brand interfaceserver and intent analyzer, according to an embodiment. According to anembodiment, a callback cloud 520 may interface with a brand interfaceserver 530, which may interface with third-party or proprietary brandsof communications devices and interfaces such as automated calldistributor systems 1405. Through this brand interface, the system mayreceive a request for a callback to a callback recipient, analyzingtheir intent from the provided input 1410, followed by processing it asa callback request 1415. Callback requestor intent in this case mayindicate how long or what times are preferred for a callback to takeplace, which may be taken into account for a callback 1410. This refersto an individual calling a user of a cloud callback system 520, beingunable to connect for any reason, and the system allowing the caller torequest a callback, thus becoming the callback requester, from thecallback recipient, the person they were initially unable to reach. Acallback object is instantiated 1420, using a callback manager 523,which is an object with data fields representing the various parts ofcallback data for a callback requester and callback recipient, and anyrelated information such as what scheduled times may be possible forsuch a callback to take place. Global profiles may then be retrieved1425 using a profile manager 521 in a cloud callback system, as well asan analysis of environmental context data 1430, allowing for the systemto determine times when a callback may be possible for a callbackrequestor and callback recipient both 1435. When such a time arrives, afirst callback is attempted 1440 to the callback requestor or callbackrecipient, and if this succeeds, a second call is attempted to thesecond of the callback requestor and callback recipient 1445, allowing amedia server 525 to bridge the connection when both are online, beforedeleting the callback object 1450.

FIG. 15 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a privacy server,according to an embodiment. According to an embodiment, a callback cloud620 must receive a request for a callback to a callback recipient, froma callback requester 1505. This refers to an individual calling a userof a cloud callback system 620, being unable to connect for any reason,and the system allowing the caller to request a callback, thus becomingthe callback requester, from the callback recipient, the person theywere initially unable to reach. When a callback request is received1505, trust-circle rules are enforced using a privacy server 621, 1510preventing untrusted users from requesting a callback, or insufficientlytrusted users from scheduling callbacks at specific times or perhapspreventing them from requesting callbacks with certain callbackrecipients, depending on the privacy settings of a given callbackrecipient. All data may also be encrypted 1515 for added security, usinga privacy server 621. If a callback request is allowed to proceed, acallback object is instantiated 1520, using a callback manager 624,which is an object with data fields representing the various parts ofcallback data for a callback requester and callback recipient, and anyrelated information such as what scheduled times may be possible forsuch a callback to take place. Global profiles may then be retrieved1525 using a profile manager 622 in a cloud callback system, as well asan analysis of environmental context data 1530, allowing for the systemto determine times when a callback may be possible for a callbackrequestor and callback recipient both 1535. When such a time arrives, afirst callback is attempted 1540 to the callback requestor or callbackrecipient, and if this succeeds, a second call is attempted to thesecond of the callback requestor and callback recipient 1545, allowing amedia server 626 to bridge the connection when both are online, beforedeleting the callback object 1550.

FIG. 16 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a bot server,according to an embodiment. According to an embodiment, a callback cloud720 may first utilize a bot server 724 to receive an automated callbackrequest from a user 1605, which may allow a user to specify theirparameters for a callback directly to the system. The system may thenreceive a request for a callback to a callback recipient, from acallback requester 1610. This refers to an individual calling a user ofa cloud callback system 720, being unable to connect for any reason, andthe system allowing the caller to request a callback, thus becoming thecallback requester, from the callback recipient, the person they wereinitially unable to reach. A callback object is instantiated 1615, usinga callback manager 723, which is an object with data fields representingthe various parts of callback data for a callback requester and callbackrecipient, and any related information such as what scheduled times maybe possible for such a callback to take place. Global profiles may thenbe retrieved 1620 using a profile manager 721 in a cloud callbacksystem, as well as an analysis of environmental context data 1625,allowing for the system to determine times when a callback may bepossible for a callback requestor and callback recipient both 1630. Whensuch a time arrives, a first callback is attempted 1635 to the callbackrequestor or callback recipient, and if this succeeds, a second call isattempted to the second of the callback requestor and callback recipient1640, allowing a media server 726 to bridge the connection when both areonline, before deleting the callback object 1645.

FIG. 17 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including an operationsanalyzer, according to an embodiment. According to an embodiment, acallback cloud 820 must receive a request for a callback to a callbackrecipient, from a callback requester 1705. This refers to an individualcalling a user of a cloud callback system 820, being unable to connectfor any reason, and the system allowing the caller to request acallback, thus becoming the callback requester, from the callbackrecipient, the person they were initially unable to reach. A callbackobject is instantiated 1710, using a callback manager 823, which is anobject with data fields representing the various parts of callback datafor a callback requester and callback recipient, and any relatedinformation such as what scheduled times may be possible for such acallback to take place. Global profiles may then be retrieved 1715 usinga profile manager 821 in a cloud callback system, as well as an analysisof environmental context data 1720, allowing for the system to determinetimes when a callback may be possible for a callback requestor andcallback recipient both 1725. When such a time arrives, a first callbackis attempted 1730 to the callback requestor or callback recipient, andif this succeeds, a second call is attempted to the second of thecallback requestor and callback recipient 1735, allowing a media server826 to bridge the connection when both are online, before deleting thecallback object 1740. An operations analyzer 824 may then monitoroperation of components and communication channels involved in thecallback, analyze the results of the attempted callback bridge, and ifit was unsuccessful, determine whether a component or communicationchannel of a callback cloud experiences a failure, and either select analternate communication channel to complete the callback at a scheduledtime or store such results 1745 for viewing by a later systemadministrator.

FIG. 18 is a method diagram illustrating the use of a callback cloud forintent-based active callback management, including a brand interfaceserver, intent analyzer, and broker server, according to an embodiment.According to an embodiment, a callback cloud 920 may interface with abrand interface server 930, which may interface with third-party orproprietary brands of communications devices and interfaces such asautomated call distributor systems 1805. Through this brand interface,the system may receive a request for a callback to a callback recipient,analyzing their intent from the provided input 1810, before a brokerserver 940 communicates this request to the callback cloud 920, 1820 andnot only exposes but also manages connections and interactions betweenvarious brands 910 and a callback cloud 920, 1815. The system may thenprocess a callback request 1820. Callback requestor intent in this casemay indicate how long or what times are preferred for a callback to takeplace, which may be taken into account for a callback 1810. This refersto an individual calling a user of a cloud callback system 920, beingunable to connect for any reason, and the system allowing the caller torequest a callback, thus becoming the callback requester, from thecallback recipient, the person they were initially unable to reach.After receiving at least one callback request, a broker server 940 mayfurther manage dealings between multiple callback requests and more thantwo requestors or recipients 1825, selecting a plurality of specificactions to take during a callback and allocating each selected action toa system component involved in the callback. The broker server 940 mayorganize successive or nested callback attempts by user availability andtimes available, as well as the times the requests are received 1830. Atleast one callback object is then instantiated 1835, using a callbackmanager 923, which is an object with data fields representing thevarious parts of callback data for a callback requester and callbackrecipient, and any related information such as what scheduled times maybe possible for such a callback to take place. Global profiles may thenbe retrieved 1840 using a profile manager 921 in a cloud callbacksystem, as well as an analysis of environmental context data 1845,allowing for the system to determine times when a callback may bepossible for a callback requestor and callback recipient both 1850. Whensuch a time arrives, a first callback is attempted 1855 to the callbackrequestor or callback recipient, and if this succeeds, a second call isattempted to the second of the callback requestor and callback recipient1860, allowing a media server 925 to bridge the connection when both areonline, before deleting the callback object 1865.

FIG. 19 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, according to an embodiment. Key componentsexchanging messages in this embodiment include a callback manager 1905,a profile manager 1910, an environment analyzer 1915, an interactionmanager 1920, and a media server 1925. A callback request is made 1930,which is forwarded to a callback manager 1915. A callback manager thenrequests profile information on a callback requestor and recipient 1935,a profile manager 1910 then requesting environmental context 1940 froman environment analyzer 1915. Profile information and environmentalcontext information are both sent to the callback manager 1945, beforean interaction manager is sent the time for an attempted callback 1950,which then, at the designated time, sends the relevant IP addresses,usernames, phone numbers, or other pertinent connection information to amedia server 1955. The call results are sent back to an interactionmanager 1960, which then sends the finished result of the attempt atbridging the callback to the callback manager 1965.

FIG. 20 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a calendar server, according to anembodiment. Key components exchanging messages in this embodimentinclude a callback manager 2005, a profile manager 2010, an environmentanalyzer 2015, an interaction manager 2020, a media server 2025, and acalendar server 2030. A callback request is made 2035, which isforwarded to a callback manager 2015. A callback manager then requestsprofile information on a callback requestor and recipient 2040, aprofile manager 2010 then requesting environmental context 2045 from anenvironment analyzer 2015. Profile information and environmental contextinformation are both sent to the callback manager 2050, before a profilemanager may request calendar schedules 2055 from both a callbackrequestor and a callback recipient, using a calendar server 2030. Ifcalendars are available for either or both users, they are forwarded tothe callback manager 2060. The interaction manager is then sent the timefor an attempted callback 2065, which then, at the designated time,sends the relevant IP addresses, usernames, phone numbers, or otherpertinent connection information to a media server 2070. The callresults are sent back to an interaction manager 2075, which then sendsthe finished result of the attempt at bridging the callback to thecallback manager 2080.

FIG. 21 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server, according to anembodiment. Key components exchanging messages in this embodimentinclude a callback manager 2105, a profile manager 2110, an environmentanalyzer 2115, an interaction manager 2120, a media server 2125, and abrand interface server 2130. A callback request is made 2135, which isforwarded to a callback manager 2115. A brand interface server mayidentify the devices or services communicating with the callback cloudsystem 2140, and possibly allow for communication back to such servicesand devices. A callback manager then requests profile information on acallback requestor and recipient 2145, a profile manager 2110 thenrequesting environmental context 2150 from an environment analyzer 2115.Profile information and environmental context information are both sentto the callback manager 2155, before an interaction manager is sent thetime for an attempted callback 2160, which then, at the designated time,sends the relevant IP addresses, usernames, phone numbers, or otherpertinent connection information to a media server 2165. The callresults are sent back to an interaction manager 2170, which then sendsthe finished result of the attempt at bridging the callback to thecallback manager 2175.

FIG. 22 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server and intentanalyzer, according to an embodiment. Key components exchanging messagesin this embodiment include a callback manager 2205, a profile manager2210, an environment analyzer 2215, an interaction manager 2220, a mediaserver 2225, a brand interface server 2230, and an intent analyzer 2235.After a callback request is made, a brand interface server may forwardraw data from the services or applications used in making the request toan intent analyzer 2240, before identifying the devices or servicescommunicating with the callback cloud system 2245 and sending such datato a callback manager. An intent analyzer may then send data on callbackrequest intent 2250 to a callback manager 2205, which may indicate suchthings as the time a user may want to receive a callback, or what daysthey may be available, or how long the callback may take, which mayaffect the availability of timeslots for both a callback requestor andrecipient. A callback manager then requests profile information on acallback requestor and recipient 2255, a profile manager 2210 thenrequesting environmental context 2260 from an environment analyzer 2215.Profile information and environmental context information are both sentto the callback manager 2265, before an interaction manager is sent thetime for an attempted callback 2270, which then, at the designated time,sends the relevant IP addresses, usernames, phone numbers, or otherpertinent connection information to a media server 2275. The callresults are sent back to an interaction manager 2280, which then sendsthe finished result of the attempt at bridging the callback to thecallback manager 2285.

FIG. 23 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a privacy server, according to anembodiment. Key components exchanging messages in this embodimentinclude a callback manager 2305, a profile manager 2310, an environmentanalyzer 2315, an interaction manager 2320, a media server 2325, and aprivacy server 2330. A callback request is made 2335, which is forwardedto a callback manager 2315. A callback manager may then request privacysettings 2340 from a privacy server 2330, being forwarded the privacysettings 2345 from said server, including information on a user's trustcircles as needed. A callback manager 2305 then requests profileinformation on a callback requestor and recipient 2350, a profilemanager 2310 then requesting environmental context 2355 from anenvironment analyzer 2315. Profile information and environmental contextinformation are both sent to the callback manager 2360, before aninteraction manager is sent the time for an attempted callback 2365,which then, at the designated time, sends the relevant IP addresses,usernames, phone numbers, or other pertinent connection information to amedia server 2370. The call results are sent back to an interactionmanager 2375, which then sends the finished result of the attempt atbridging the callback to the callback manager 2380.

FIG. 24 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a bot server, according to an embodiment.Key components exchanging messages in this embodiment include a callbackmanager 2405, a profile manager 2410, an environment analyzer 2415, aninteraction manager 2420, a media server 2425, and a bot server 2430. Acallback request is made 2435, which is forwarded to a bot server 2430.A bot server may handle a user in a similar manner to an automated calldistribution server for example, allowing a user to communicate verballyor textually with it, or it may instead handle results from a chatserver and parse the results of a user interacting with another chatserver 715. A callback manager may then receive parsed callback data2440 from a bot server 2430. A callback manager 2405 then requestsprofile information on a callback requestor and recipient 2445, aprofile manager 2410 then requesting environmental context 2450 from anenvironment analyzer 2415. Profile information and environmental contextinformation are both sent to the callback manager 2455, before aninteraction manager is sent the time for an attempted callback 2460,which then, at the designated time, sends the relevant IP addresses,usernames, phone numbers, or other pertinent connection information to amedia server 2465. The call results are sent back to an interactionmanager 2470, which then sends the finished result of the attempt atbridging the callback to the callback manager 2475.

FIG. 25 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including an operations analyzer, according to anembodiment. Key components exchanging messages in this embodimentinclude a callback manager 2505, a profile manager 2510, an environmentanalyzer 2515, an interaction manager 2520, a media server 2525, and anoperations analyzer 2530. A callback request is made 2535, which isforwarded to a callback manager 2505. A callback manager then requestsprofile information on a callback requestor and recipient 2540, aprofile manager 2510 then requesting environmental context 2545 from anenvironment analyzer 2515. Profile information and environmental contextinformation are both sent to the callback manager 2550, allowing acallback manager to forward initial callback object data to anoperations analyzer 2555, before an interaction manager is sent the timefor an attempted callback 2560, which then, at the designated time,sends the relevant IP addresses, usernames, phone numbers, or otherpertinent connection information to a media server 2565. The callresults are sent back to an interaction manager 2570, which then sendsthe finished result of the attempt at bridging the callback to thecallback manager 2575. At the end of this sequence, the callback resultdata, including any failures or lack of ability to bridge a call for acompleted callback between at least two users, is forwarded to anoperations analyzer 2580 for possible review by a human, if needed, andfor adjustment of the parameters the system uses in attempts to makecallbacks for said users.

FIG. 30 is a message flow diagram illustrating the exchange of messagesand data between components of a callback cloud for intent-based activecallback management, including a brand interface server, intentanalyzer, and broker server, according to an embodiment. Key componentsexchanging messages in this embodiment include a callback manager 3005,a profile manager 3010, an environment analyzer 3015, an interactionmanager 3020, a media server 3025, a brand interface server 3030, anintent analyzer 3035, and a broker server 3090. After a callback requestis made, a brand interface server may forward raw data 3040 from theservices or applications used in making the request to an intentanalyzer 3035, before identifying the devices or services communicatingwith the callback cloud system and sending such data to a broker server3090, which identifies and exposes brand information 3045 to thecallback cloud while managing connections between the callback cloud andvarious brands. An intent analyzer may then send data on callbackrequest intent 3050 to broker server 3090, which forwards thisinformation to a callback manager 3005, which may indicate such thingsas the time a user may want to receive a callback, or what days they maybe available, or how long the callback may take, which may affect theavailability of timeslots for both a callback requestor and recipient. Acallback manager then requests profile information on a callbackrequestor and recipient 3055, a profile manager 3010 then requestingenvironmental context 3060 from an environment analyzer 3015. Profileinformation and environmental context information are both sent to thecallback manager 3065, before an interaction manager is sent the timefor an attempted callback 3070, which then, at the designated time,sends the relevant IP addresses, usernames, phone numbers, or otherpertinent connection information to a media server 3075. The callresults are sent back to an interaction manager 3080, which then sendsthe finished result of the attempt at bridging the callback to thecallback manager 3085.

Hardware Architecture

Generally, the techniques disclosed herein may be implemented onhardware or a combination of software and hardware. For example, theymay be implemented in an operating system kernel, in a separate userprocess, in a library package bound into network applications, on aspecially constructed machine, on an application-specific integratedcircuit (“ASIC”), or on a network interface card.

Software/hardware hybrid implementations of at least some of the aspectsdisclosed herein may be implemented on a programmable network-residentmachine (which should be understood to include intermittently connectednetwork-aware machines) selectively activated or reconfigured by acomputer program stored in memory. Such network devices may havemultiple network interfaces that may be configured or designed toutilize different types of network communication protocols. A generalarchitecture for some of these machines may be described herein in orderto illustrate one or more exemplary means by which a given unit offunctionality may be implemented. According to specific aspects, atleast some of the features or functionalities of the various aspectsdisclosed herein may be implemented on one or more general-purposecomputers associated with one or more networks, such as for example anend-user computer system, a client computer, a network server or otherserver system, a mobile computing device (e.g., tablet computing device,mobile phone, smartphone, laptop, or other appropriate computingdevice), a consumer electronic device, a music player, or any othersuitable electronic device, router, switch, or other suitable device, orany combination thereof. In at least some aspects, at least some of thefeatures or functionalities of the various aspects disclosed herein maybe implemented in one or more virtualized computing environments (e.g.,network computing clouds, virtual machines hosted on one or morephysical computing machines, or other appropriate virtual environments).

Referring now to FIG. 26, there is shown a block diagram depicting anexemplary computing device 10 suitable for implementing at least aportion of the features or functionalities disclosed herein. Computingdevice 10 may be, for example, any one of the computing machines listedin the previous paragraph, or indeed any other electronic device capableof executing software- or hardware-based instructions according to oneor more programs stored in memory. Computing device 10 may be configuredto communicate with a plurality of other computing devices, such asclients or servers, over communications networks such as a wide areanetwork a metropolitan area network, a local area network, a wirelessnetwork, the Internet, or any other network, using known protocols forsuch communication, whether wireless or wired.

In one embodiment, computing device 10 includes one or more centralprocessing units (CPU) 12, one or more interfaces 15, and one or morebusses 14 (such as a peripheral component interconnect (PCI) bus). Whenacting under the control of appropriate software or firmware, CPU 12 maybe responsible for implementing specific functions associated with thefunctions of a specifically configured computing device or machine. Forexample, in at least one embodiment, a computing device 10 may beconfigured or designed to function as a server system utilizing CPU 12,local memory 11 and/or remote memory 16, and interface(s) 15. In atleast one embodiment, CPU 12 may be caused to perform one or more of thedifferent types of functions and/or operations under the control ofsoftware modules or components, which for example, may include anoperating system and any appropriate applications software, drivers, andthe like.

CPU 12 may include one or more processors 13 such as, for example, aprocessor from one of the Intel, ARM, Qualcomm, and AMD families ofmicroprocessors. In some embodiments, processors 13 may includespecially designed hardware such as application-specific integratedcircuits (ASICs), electrically erasable programmable read-only memories(EEPROMs), field-programmable gate arrays (FPGAs), and so forth, forcontrolling operations of computing device 10. In a specific embodiment,a local memory 11 (such as non-volatile random access memory (RAM)and/or read-only memory (ROM), including for example one or more levelsof cached memory) may also form part of CPU 12. However, there are manydifferent ways in which memory may be coupled to system 10. Memory 11may be used for a variety of purposes such as, for example, cachingand/or storing data, programming instructions, and the like. It shouldbe further appreciated that CPU 12 may be one of a variety ofsystem-on-a-chip (SOC) type hardware that may include additionalhardware such as memory or graphics processing chips, such as a QUALCOMMSNAPDRAGON™ or SAMSUNG EXYNOS™ CPU as are becoming increasingly commonin the art, such as for use in mobile devices or integrated devices.

As used herein, the term “processor” is not limited merely to thoseintegrated circuits referred to in the art as a processor, a mobileprocessor, or a microprocessor, but broadly refers to a microcontroller,a microcomputer, a programmable logic controller, anapplication-specific integrated circuit, and any other programmablecircuit.

In one embodiment, interfaces 15 are provided as network interface cards(NICs). Generally, NICs control the sending and receiving of datapackets over a computer network; other types of interfaces 15 may forexample support other peripherals used with computing device 10. Amongthe interfaces that may be provided are Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces,graphics interfaces, and the like. In addition, various types ofinterfaces may be provided such as, for example, universal serial bus(USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radiofrequency (RF), BLUETOOTH™, near-field communications (e.g., usingnear-field magnetics), 802.11 (Wi-Fi), frame relay, TCP/IP, ISDN, fastEthernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) orexternal SATA (ESATA) interfaces, high-definition multimedia interface(HDMI), digital visual interface (DVI), analog or digital audiointerfaces, asynchronous transfer mode (ATM) interfaces, high-speedserial interface (HSSI) interfaces, Point of Sale (POS) interfaces,fiber data distributed interfaces (FDDIs), and the like. Generally, suchinterfaces 15 may include physical ports appropriate for communicationwith appropriate media. In some cases, they may also include anindependent processor (such as a dedicated audio or video processor, asis common in the art for high-fidelity A/V hardware interfaces) and, insome instances, volatile and/or non-volatile memory (e.g., RAM).

Although the system shown in FIG. 26 illustrates one specificarchitecture for a computing device 10 for implementing one or more ofthe inventions described herein, it is by no means the only devicearchitecture on which at least a portion of the features and techniquesdescribed herein may be implemented. For example, architectures havingone or any number of processors 13 may be used, and such processors 13may be present in a single device or distributed among any number ofdevices. In one embodiment, a single processor 13 handles communicationsas well as routing computations, while in other embodiments a separatededicated communications processor may be provided. In variousembodiments, different types of features or functionalities may beimplemented in a system according to the invention that includes aclient device (such as a tablet device or smartphone running clientsoftware) and server systems (such as a server system described in moredetail below).

Regardless of network device configuration, the system of the presentinvention may employ one or more memories or memory modules (such as,for example, remote memory block 16 and local memory 11) configured tostore data, program instructions for the general-purpose networkoperations, or other information relating to the functionality of theembodiments described herein (or any combinations of the above). Programinstructions may control execution of or comprise an operating systemand/or one or more applications, for example. Memory 16 or memories 11,16 may also be configured to store data structures, configuration data,encryption data, historical system operations information, or any otherspecific or generic non-program information described herein.

Because such information and program instructions may be employed toimplement one or more systems or methods described herein, at least somenetwork device embodiments may include nontransitory machine-readablestorage media, which, for example, may be configured or designed tostore program instructions, state information, and the like forperforming various operations described herein. Examples of suchnontransitory machine-readable storage media include, but are notlimited to, magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks, and hardware devices that are speciallyconfigured to store and perform program instructions, such as read-onlymemory devices (ROM), flash memory (as is common in mobile devices andintegrated systems), solid state drives (SSD) and “hybrid SSD” storagedrives that may combine physical components of solid state and hard diskdrives in a single hardware device (as are becoming increasingly commonin the art with regard to personal computers), memristor memory, randomaccess memory (RAM), and the like. It should be appreciated that suchstorage means may be integral and non-removable (such as RAM hardwaremodules that may be soldered onto a motherboard or otherwise integratedinto an electronic device), or they may be removable such as swappableflash memory modules (such as “thumb drives” or other removable mediadesigned for rapidly exchanging physical storage devices),“hot-swappable” hard disk drives or solid state drives, removableoptical storage discs, or other such removable media, and that suchintegral and removable storage media may be utilized interchangeably.Examples of program instructions include both object code, such as maybe produced by a compiler, machine code, such as may be produced by anassembler or a linker, byte code, such as may be generated by forexample a JAVA™ compiler and may be executed using a Java virtualmachine or equivalent, or files containing higher level code that may beexecuted by the computer using an interpreter (for example, scriptswritten in Python, Perl, Ruby, Groovy, or any other scripting language).

In some embodiments, systems according to the present invention may beimplemented on a standalone computing system. Referring now to FIG. 27,there is shown a block diagram depicting a typical exemplaryarchitecture of one or more embodiments or components thereof on astandalone computing system. Computing device 20 includes processors 21that may run software that carry out one or more functions orapplications of embodiments of the invention, such as for example aclient application 24. Processors 21 may carry out computinginstructions under control of an operating system 22 such as, forexample, a version of MICROSOFT WINDOWS™ operating system, APPLE OSX™ oriOS™ operating systems, some variety of the Linux operating system,ANDROID™ operating system, or the like. In many cases, one or moreshared services 23 may be operable in system 20, and may be useful forproviding common services to client applications 24. Services 23 may forexample be WINDOWS™ services, user-space common services in a Linuxenvironment, or any other type of common service architecture used withoperating system 21. Input devices 28 may be of any type suitable forreceiving user input, including for example a keyboard, touchscreen,microphone (for example, for voice input), mouse, touchpad, trackball,or any combination thereof. Output devices 27 may be of any typesuitable for providing output to one or more users, whether remote orlocal to system 20, and may include for example one or more screens forvisual output, speakers, printers, or any combination thereof. Memory 25may be random-access memory having any structure and architecture knownin the art, for use by processors 21, for example to run software.Storage devices 26 may be any magnetic, optical, mechanical, memristor,or electrical storage device for storage of data in digital form (suchas those described above, referring to FIG. 26). Examples of storagedevices 26 include flash memory, magnetic hard drive, CD-ROM, and/or thelike.

In some embodiments, systems of the present invention may be implementedon a distributed computing network, such as one having any number ofclients and/or servers. Referring now to FIG. 28, there is shown a blockdiagram depicting an exemplary architecture 30 for implementing at leasta portion of a system according to an embodiment of the invention on adistributed computing network. According to the embodiment, any numberof clients 33 may be provided. Each client 33 may run software forimplementing client-side portions of the present invention; clients maycomprise a system 20 such as that illustrated in FIG. 27. In addition,any number of servers 32 may be provided for handling requests receivedfrom one or more clients 33. Clients 33 and servers 32 may communicatewith one another via one or more electronic networks 31, which may be invarious embodiments any of the Internet, a wide area network, a mobiletelephony network (such as CDMA or GSM cellular networks), a wirelessnetwork (such as WiFi, WiMAX, LTE, and so forth), or a local areanetwork (or indeed any network topology known in the art; the inventiondoes not prefer any one network topology over any other). Networks 31may be implemented using any known network protocols, including forexample wired and/or wireless protocols.

In addition, in some embodiments, servers 32 may call external services37 when needed to obtain additional information, or to refer toadditional data concerning a particular call. Communications withexternal services 37 may take place, for example, via one or morenetworks 31. In various embodiments, external services 37 may compriseweb-enabled services or functionality related to or installed on thehardware device itself. For example, in an embodiment where clientapplications 24 are implemented on a smartphone or other electronicdevice, client applications 24 may obtain information stored in a serversystem 32 in the cloud or on an external service 37 deployed on one ormore of a particular enterprise's or user's premises.

In some embodiments of the invention, clients 33 or servers 32 (or both)may make use of one or more specialized services or appliances that maybe deployed locally or remotely across one or more networks 31. Forexample, one or more databases 34 may be used or referred to by one ormore embodiments of the invention. It should be understood by one havingordinary skill in the art that databases 34 may be arranged in a widevariety of architectures and using a wide variety of data access andmanipulation means. For example, in various embodiments one or moredatabases 34 may comprise a relational database system using astructured query language (SQL), while others may comprise analternative data storage technology such as those referred to in the artas “NoSQL” (for example, HADOOP CASSANDRA™, GOOGLE BIGTABLE™, and soforth). In some embodiments, variant database architectures such ascolumn-oriented databases, in-memory databases, clustered databases,distributed databases, or even flat file data repositories may be usedaccording to the invention. It will be appreciated by one havingordinary skill in the art that any combination of known or futuredatabase technologies may be used as appropriate, unless a specificdatabase technology or a specific arrangement of components is specifiedfor a particular embodiment herein. Moreover, it should be appreciatedthat the term “database” as used herein may refer to a physical databasemachine, a cluster of machines acting as a single database system, or alogical database within an overall database management system. Unless aspecific meaning is specified for a given use of the term “database”, itshould be construed to mean any of these senses of the word, all ofwhich are understood as a plain meaning of the term “database” by thosehaving ordinary skill in the art.

Similarly, most embodiments of the invention may make use of one or moresecurity systems 36 and configuration systems 35. Security andconfiguration management are common information technology (IT) and webfunctions, and some amount of each are generally associated with any ITor web systems. It should be understood by one having ordinary skill inthe art that any configuration or security subsystems known in the artnow or in the future may be used in conjunction with embodiments of theinvention without limitation, unless a specific security 36 orconfiguration system 35 or approach is specifically required by thedescription of any specific embodiment.

FIG. 29 shows an exemplary overview of a computer system 40 as may beused in any of the various locations throughout the system. It isexemplary of any computer that may execute code to process data. Variousmodifications and changes may be made to computer system 40 withoutdeparting from the broader scope of the system and method disclosedherein. Central processor unit (CPU) 41 is connected to bus 42, to whichbus is also connected memory 43, nonvolatile memory 44, display 47,input/output (I/O) unit 48, and network interface card (NIC) 53. I/Ounit 48 may, typically, be connected to keyboard 49, pointing device 50,hard disk 52, and real-time clock 51. NIC 53 connects to network 54,which may be the Internet or a local network, which local network may ormay not have connections to the Internet. Also shown as part of system40 is power supply unit 45 connected, in this example, to a mainalternating current (AC) supply 46. Not shown are batteries that couldbe present, and many other devices and modifications that are well knownbut are not applicable to the specific novel functions of the currentsystem and method disclosed herein. It should be appreciated that someor all components illustrated may be combined, such as in variousintegrated applications, for example Qualcomm or Samsungsystem-on-a-chip (SOC) devices, or whenever it may be appropriate tocombine multiple capabilities or functions into a single hardware device(for instance, in mobile devices such as smartphones, video gameconsoles, in-vehicle computer systems such as navigation or multimediasystems in automobiles, or other integrated hardware devices).

In various embodiments, functionality for implementing systems ormethods of the present invention may be distributed among any number ofclient and/or server components. For example, various software modulesmay be implemented for performing various functions in connection withthe present invention, and such modules may be variously implemented torun on server and/or client components.

The skilled person will be aware of a range of possible modifications ofthe various embodiments described above. Accordingly, the presentinvention is defined by the claims and their equivalents.

What is claimed is:
 1. A system for intent-based active callbackmanagement, comprising: a callback manager comprising at least aprocessor, a memory, and a first plurality of programming instructionsstored in the memory and operating on the processor, wherein the firstprogramming instructions, when operating on the processor, cause theprocessor to: receive a request for a callback to a callback recipientfrom a callback requester; instantiate a callback object; obtainenvironmental context for callback requester and callback recipient;update user profiles based on callback usage and performance patterns,as well as updates requested by users; determine a callback time, basedat least on at least one user profile and the environmental context, andcommunicate it back to the callback recipient and the callbackrequester; connect the two parties, when the two first and second calledparties are online, and delete the callback object; an interactionmanager comprising at least a processor, a memory, and a first pluralityof programming instructions stored in the memory and operating on theprocessor, wherein the first programming instructions, when operating onthe processor, cause the processor to: call the other of a callbackrequester and callback recipient, when the first called party is online,as a second called party; connect the two parties, when the two firstand second called parties are online, and delete the callback object; amedia server comprising at least a processor, a memory, and a firstplurality of programming instructions stored in the memory and operatingon the processor, wherein the first programming instructions, whenoperating on the processor, cause the processor to: make calls andbridge them when appropriate, under control of the interaction manager;and an environment analyzer comprising at least a processor, a memory,and a first plurality of programming instructions stored in the memoryand operating on the processor, wherein the first programminginstructions, when operating on the processor, cause the processor to:analyze environment context data pertaining to the callback requesterand the callback recipient.
 2. The system of claim 1, further comprisinga calendar server comprising at least a processor, a memory, and a firstplurality of programming instructions stored in the memory and operatingon the processor, wherein the first programming instructions, whenoperating on the processor, cause the processor to: interface with aplurality of user-specific calendars; and identify timeslots when thecallback requester and recipient will both be available.
 3. The systemof claim 1, further comprising a brand interface server comprising atleast a processor, a memory, and a first plurality of programminginstructions stored in the memory and operating on the processor,wherein the first programming instructions, when operating on theprocessor, cause the processor to: connect to a plurality of externalservices; identify an external service to the callback manager; andexpose any available APIs of the identified external service to thecallback manager.
 4. The system of claim 3, further comprising an intentanalyzer comprising at least a processor, a memory, and a firstplurality of programming instructions stored in the memory and operatingon the processor, wherein the first programming instructions, whenoperating on the processor, cause the processor to: analyze a callbackrequest to determine the context of the request; wherein the analysiscomprises at least one operation drawn from the set of text analytics,speech-to-text transcription, audio analysis, facial recognition,expression analysis, and posture analysis.
 5. The system of claim 1,further comprising a privacy server comprising at least a processor, amemory, and a first plurality of programming instructions stored in thememory and operating on the processor, wherein the first programminginstructions, when operating on the processor, cause the processor to:identify a callback requestor; verify the callback requestor's identityagainst a trust configuration to determine whether the callbackrequestor is considered a trusted user; if the callback requestor is nota trusted user, deny the callback request; and encrypt at least one datastream involved in a callback.
 6. The system of claim 1, furthercomprising a bot server comprising at least a processor, a memory, and afirst plurality of programming instructions stored in the memory andoperating on the processor, wherein the first programming instructions,when operating on the processor, cause the processor to: receive aplurality of callback parameters from the callback requestor; andprovide the callback parameters to a callback manager.
 7. The system ofclaim 1, further comprising an operations analyzer comprising at least aprocessor, a memory, and a first plurality of programming instructionsstored in the memory and operating on the processor, wherein the firstprogramming instructions, when operating on the processor, cause theprocessor to: determine a particular communication channel to use for acallback; monitor operation of components and communication channelsinvolved in the callback; and if a component or communication channel ofa callback cloud experiences a failure, select an alternatecommunication channel to complete the callback at a scheduled time. 8.The system of claim 4, further comprising a broker server comprising atleast a processor, a memory, and a first plurality of programminginstructions stored in the memory and operating on the processor,wherein the first programming instructions, when operating on theprocessor, cause the processor to: select a plurality of specificactions to take during a callback; and allocate each selected action toa system component involved in the callback.
 9. A method forintent-based active callback management, comprising the steps of:receiving a request for a callback to a callback recipient from acallback requester; instantiate a callback object; retrieving userprofiles for the callback requester and the callback recipient;obtaining environmental context for callback requester and callbackrecipient; determining a callback time based on at least one retrieveduser profile and an environmental context, and communicating thedetermined callback time to the callback recipient and the callbackrequester; attempting a call to a first called party when a callbacktime arrives, the first called party being one of either the callbackrequester or callback recipient; calling as a second called party, theother of the callback requester and callback recipients, when the firstcalled party is online; updating user profiles based on callback usageand performance patterns, as well as updates requested by users; andconnecting the two first and second called parties when the secondcalled party is online, and delete the callback object.
 10. The methodof claim 9, further including the steps of: obtaining a plurality ofscheduled events from a calendar from the callback requester; anddetermining the callback time by determining when the requesting user isavailable for a callback, referencing the plurality of scheduled events.11. The method of claim 9, further including the steps of: interfacingwith a plurality of user-specific calendars using a calendar server; andidentifying time slots when the callback requester and callbackrecipient will both be available.
 12. The method of claim 9, furthercomprising the steps of: connecting to a plurality of external servicesusing a brand interface server; identifying an external service to thecallback manager; and exposing any available APIs of the identifiedexternal service to the callback manager.
 13. The method of claim 12,further comprising the steps of: analyzing a callback request todetermine the context of the request, using an intent analyzer; whereinthe analysis comprises at least one operation drawn from the set of textanalytics, speech-to-text transcription, audio analysis, facialrecognition, expression analysis, and posture analysis.
 14. The methodof claim 9, further comprising the steps of: identifying a callbackrequestor, using a privacy server; verifying the callback requestor'sidentity against a trust configuration to determine whether the callbackrequestor is considered a trusted user; if the callback requestor is nota trusted user, denying the callback request; and encrypting at leastone data stream involved in a callback.
 15. The method of claim 9,further comprising the steps of: receiving a plurality of callbackparameters from the callback requestor, using a bot server; andproviding the callback parameters to a callback manager.
 16. The methodof claim 9, further comprising the steps of: determining a particularcommunication channel to use for a callback, using an operationsanalyzer; monitoring operation of components and communication channelsinvolved in the callback; and if a component or communication channel ofa callback cloud experiences a failure, selecting an alternatecommunication channel to complete the callback at a scheduled time. 17.The method of claim 13, further comprising the steps of: selecting aplurality of specific actions to take during a callback, using a brokerserver; and allocating each selected action to a system componentinvolved in the callback.